Thick and thin data volume management

ABSTRACT

Methods, apparatus and computer program products implement embodiments of the present invention that include configuring one or more storage devices as a plurality of physical storage units, each of the physical storage units having a storage granularity, and configuring, on the one or more storage devices, a thin provisioned storage pool having a physical number of the physical storage units and a logical number of logical storage units, the physical number being less than the logical number. Upon receiving a request to create a thick data volume having a requested number of the physical storage units, an available number of the physical storage units that are available in the thin provisioned pool can be identified. Upon determining that the requested number is less than the available number, the requested number of the physical storage units can be allocated, from the thin provisioned storage pool, to the thick data volume.

FIELD OF THE INVENTION

The present invention relates generally to data storage, andspecifically to managing thick and thin data volumes created in thin andthick provisioned storage pools.

BACKGROUND

In computer storage arrays (also referred to herein as storage systemsor storage subsystems), disk partitioning and logical volume managementare used to manage physical storage devices such as hard disk drives. Indisk partitioning, a single storage device is divided into multiplelogical storage units referred to as partitions, thereby treating onephysical storage device as if it were multiple disks. Logical volumemanagement provides a method of allocating space on mass-storage devicesthat is more flexible than conventional partitioning schemes. Inparticular, a volume manager can concatenate, stripe together orotherwise combine regions (a region is a sequence of bytes having aspecific length, typically one megabyte) into larger virtual regionsthat administrators can re-size or move, potentially withoutinterrupting system use.

The description above is presented as a general overview of related artin this field and should not be construed as an admission that any ofthe information it contains constitutes prior art against the presentpatent application.

SUMMARY

There is provided, in accordance with an embodiment of the presentinvention a storage system, including one or more storage devices, and aprocessor arranged to configure the one or more storage devices as aplurality of physical storage units, each of the physical storage unitshaving a storage granularity, to configure, on the one or more storagedevices, a thin provisioned storage pool having a physical number of thephysical storage units and a logical number of logical storage units,the physical number being less than the logical number, and uponreceiving a request to create a thick data volume having a requestednumber of the physical storage units, to identify an available number ofthe physical storage units that are available in the thin provisionedpool, and upon determining that the requested number is less than theavailable number, to allocate, from the thin provisioned storage pool,the requested number of the physical storage units to the thick datavolume.

There is also provided, in accordance with an embodiment of the presentinvention a storage system, including one or more storage devices, and aprocessor arranged to configure the one or more storage devices as aplurality of physical storage units, each of the physical storage unitshaving a storage granularity, to receive a request to create a requestedmultiple of data volumes, each of the requested multiple of the datavolumes having a requested maximum physical size, to determine, inresponse to the storage granularity, a minimum number of the physicalstorage units whose total storage size is greater than or equal to atotal of the requested physical sizes, to allocate, the minimum numberof the physical storage units from the one or more of the storagedevices, and to store, to the allocated physical storage units, therequested multiple of the data volumes contiguously in an end-to-endconfiguration.

There is further provided, in accordance with an embodiment of thepresent invention a storage system, including one or more storagedevices, and a processor arranged to configure the one or more storagedevices as a plurality of physical storage units, to configure multiplestorage pools, each of the multiple storage pools having one or morerespective pool attributes, to define a grouped pool including themultiple storage pools, and upon receiving a request to create a datavolume having one or more volume attributes and including a requestednumber of the physical storage units to identify a given storage pool inresponse to a comparison between the one or more pool attributes thereofand the one or more volume attributes thereof, to detect an availablenumber of the physical storage units in the given storage pool, and upondetermining that the requested number of the physical storage units isgreater than the available number of the physical storage units, tocompute a number including the available number of the physical storageunits subtracted from the requested number of the physical storageunits, and to transfer, within the grouped pool, the computed number ofthe physical storage units to the identified storage pool.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is herein described, by way of example only, withreference to the accompanying drawings, wherein:

FIG. 1 is a block diagram that schematically illustrates a storagesystem, in accordance with an embodiment of the present invention;

FIG. 2 is a block diagram of a module of the storage system arranged tomanage thick and thin data volumes in thick and thin provisioned storagepools, in accordance with an embodiment of the present invention;

FIG. 3 is a flow diagram that schematically illustrates a method ofcreating a given thick volume in a thin provisioned storage pool, inaccordance with a first embodiment of the present invention;

FIGS. 4A and 4B are block diagrams of storage units in the storagesystem storing multiple data volumes in an end-to-end configuration, inaccordance with a second embodiment of the present invention;

FIG. 5 is a flow diagram that schematically illustrates a method ofstoring multiple data volumes in an end-to-end configuration, inaccordance with the second embodiment of the present invention; and

FIG. 6 is a flow diagram that schematically illustrates a method ofmanaging a grouped storage pool, in accordance with a third embodimentof the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Thin provisioning is a method used in storage system to optimizeutilization of available storage. Instead of allocating all requestedphysical blocks of data (referred to herein as storage units) to datavolumes up front, thin provisioning implements on-demand allocation ofthe storage units to the data volumes. This methodology helps eliminatealmost all “whitespace” (i.e., storage units allocated to data volumesbut not storing any data), thereby improving storage utilization ratesover storage allocation methods such as thick provisioning thatallocate, to individual data volumes, storage units that may remainunused (i.e., not storing any data).

Thin provisioning implements an over-allocation (or over-subscription)mechanism that enables a storage system to view additional storagecapacity than has been physically reserved on the storage system itself.In thin provisioning, physical storage space is either physical storagespace or logical storage space, wherein the physical storage space iseither reserved or used. Reserved physical storage space comprises anamount of storage space that is allocated to a storage pool (storagepools are described hereinbelow), and used storage space comprises anamount of reserved physical storage space that is currently used tostore data. For a given data volume, the logical space comprises thegiven volume's reported capacity, and for a given storage pool, thelogical space comprises a maximum size for all data volumes in the pool.

Over-allocation enables flexibility in growth of data volumes, withouthaving to predict accurately how much a given data volume will grow.Instead, storage unit growth becomes sequential. Physical storagecapacity on the array is only dedicated when data is actually written bya host computer (or another entity such as a SCSI host or a server), notwhen the storage volume is initially allocated. The servers, and byextension the applications that reside on them, view a full size datavolume from the storage but the storage itself only allocates the blocksof data when they are written.

In storage systems implementing thin provisioning, data volumes can becreated from storage pools, wherein the data volumes are either thickvolumes or thin volumes and wherein the storage pools are either thinprovisioned pools or thick provisioned pools. A storage pool whoselogical size is greater than its physical size is can be referred to asa thin provisioned storage pool, and a storage pool whose logical sizeequals its physical size can be referred to as a thick provisioned pool.Likewise, a data volume whose logical size is greater than its physicalsize is can be referred to as a thin volume, and a data volume whoselogical size equals its physical size can be referred to as a thickvolume. In some embodiments, a thick volume may comprise a given volumecreated as a thin volume, but whose physical size equals its logicalsize (i.e., a fully allocated thin volume).

Embodiments of the present invention provide methods and systems formanaging thin and thick provisioned storage pools in order to createthick and thin volumes. As described hereinbelow, a first embodimentincludes methods and systems for creating a thick volume from a thinlyprovisioned pool, a second embodiment includes methods and systems forstoring multiple data volumes “end-to-end” in one or more storage units,and a third embodiment includes methods and systems for defining andmanaging a grouped pool that includes multiple thick and/or thinprovisioned storage pools.

In the first embodiment, one or more storage devices can be configuredas a plurality of physical storage units, wherein each of the physicalstorage units has a storage granularity. Subsequent to configuring theone or more storage devices, a thin provisioned storage pool can beconfigured on the one or more storage devices, wherein the thinprovisioned storage pool has a physical number of the physical storageunits and a logical number of logical storage units, the physical numberbeing less than the logical number. Upon receiving a request to create athick data volume having a requested number of the physical storageunits, an available number of the physical storage units that areavailable in the thin provisioned pool can be identified. Upondetermining that the requested number is less than the available number,the requested number of the physical storage units can be allocated fromthe thin provisioned storage to the thick data volume.

In the second embodiment, one or more storage devices can be configuredas a plurality of physical storage units, wherein each of the physicalstorage units has a storage granularity. Subsequent to configuring theone or more storage devices, a request can be received to create arequested multiple of data volumes, wherein each of the requestedmultiple of the data volumes has a requested maximum physical size. Inresponse to the storage granularity, a minimum number of the physicalstorage units can be determined whose total storage size is greater thanor equal to a total of the requested physical size. The determinedminimum number of the physical storage units can be allocated from theone or more of the storage devices, and the requested multiple of thedata volumes can be stored, to the allocated physical storage units,contiguously and in an end-to-end configuration.

In the third embodiment, one or more storage devices can be configuredas a plurality of physical storage units. Subsequent to configuring theone or more storage devices, multiple storage pools can be configured,wherein each of the multiple storage pools has one or more respectivepool attributes, and a grouped pool can be defined, the grouped poolcomprising the multiple storage pools. Upon receiving a request tocreate a data volume having one or more volume attributes and comprisinga requested number of the physical storage units, a given storage poolcan be identified in response to a comparison between the one or morepool attributes thereof and the one or more volume attributes thereof.Subsequent to identifying the given storage pool, an available number ofthe physical storage units in the given storage pool can be detected.Upon determining that the requested number of the physical storage unitsis greater than the available number of the physical storage units, anumber can be computed comprising the available number of the physicalstorage units subtracted from the requested number of the physicalstorage units, and the computed number of the physical storage units canbe transferred, from within the grouped pool, to the identified storagepool.

When executing a hypervisor to implement multiple virtual machine eachhaving virtualized storage, in addition to a given data volume used by agiven virtual machine, a respective meta volume is typically defined tostore configuration data for the virtual machine and its respectivevirtualized storage. As the storage systems support increasing numbersof virtual machine instances, embodiments of the present inventionenable the storage systems to utilize storage space more efficiently.

FIG. 1 is a block diagram that schematically illustrates a dataprocessing storage subsystem 20, in accordance with an embodiment of theinvention. The particular subsystem (also referred to herein as astorage system) shown in FIG. 1 is presented to facilitate anexplanation of the invention. However, as the skilled artisan willappreciate, the invention can be practiced using other computingenvironments, such as other storage subsystems with diversearchitectures and capabilities.

Storage subsystem 20 receives, from one or more host computers 22,input/output (I/O) requests, which are commands to read or write data atlogical addresses on data volumes. Any number of host computers 22 arecoupled to storage subsystem 20 by any means known in the art, forexample, using a network. Herein, by way of example, host computers 22and storage subsystem 20 are assumed to be coupled by a Storage AreaNetwork (SAN) 26 incorporating data connections 24 and Host Bus Adapters(HBAs) 28. The logical addresses specify a range of data blocks within adata volume, each block herein being assumed by way of example tocontain 512 bytes. For example, a 10 KB data record used in a dataprocessing application on a given host computer 22 would require 20blocks, which the given host computer might specify as being stored at alogical address comprising blocks 1,000 through 1,019 of a data volume.Storage subsystem 20 may operate in, or as, a SAN system.

Storage subsystem 20 comprises a clustered storage controller 34 coupledbetween SAN 26 and a private network 46 using data connections 30 and44, respectively, and incorporating adapters 32 and 42, againrespectively. In some configurations, adapters 32 and 42 may comprisehost bus adapters (HBAs) or an InfiniBand™ fabric. Clustered storagecontroller 34 implements clusters of storage modules 36, some of whichinclude an interface 38 (in communication between adapters 32 and 42),and a cache 40. Each storage module 36 is responsible for a number ofstorage devices 50 by way of a data connection 48 as shown.

As described previously, each storage module 36 further comprises agiven cache 40. However, it will be appreciated that the number ofcaches 40 used in storage subsystem 20 and in conjunction with clusteredstorage controller 34 may be any convenient number. While all caches 40in storage subsystem 20 may operate in substantially the same manner andcomprise substantially similar elements, this is not a requirement. Eachof the caches 40 may be approximately equal in size and is assumed to becoupled, by way of example, in a one-to-one correspondence with a set ofphysical storage devices 50, which may comprise disks. In oneembodiment, physical storage devices may comprise such disks. Thoseskilled in the art will be able to adapt the description herein tocaches of different sizes.

Each set of storage devices 50 comprises multiple slow and/or fastaccess time mass storage devices, herein below assumed to be multiplehard disks. FIG. 1 shows caches 40 coupled to respective sets of storagedevices 50. In some configurations, the sets of storage devices 50comprise one or more hard disks, or solid state drives (SSDs) which canhave different performance characteristics. In response to an I/Ocommand, a given cache 40, by way of example, may read or write data ataddressable physical locations of a given storage device 50. In theembodiment shown in FIG. 1, caches 40 are able to exercise certaincontrol functions over storage devices 50. These control functions mayalternatively be realized by hardware devices such as disk controllers(not shown), which are linked to caches 40.

Each storage module 36 is operative to monitor its state, including thestates of associated caches 40, and to transmit configurationinformation to other components of storage subsystem 20 for example,configuration changes that result in blocking intervals, or limit therate at which I/O requests for the sets of physical storage areaccepted.

Routing of commands and data from HBAs 28 to clustered storagecontroller 34 and to each cache 40 may be performed over a networkand/or a switch. Herein, by way of example, HBAs 28 may be coupled tostorage modules 36 by at least one switch (not shown) of SAN 26, whichcan be of any known type having a digital cross-connect function.Additionally or alternatively, HBAs 28 may be coupled to storage modules36.

In some embodiments, data having contiguous logical addresses can bedistributed among modules 36, and within the storage devices in each ofthe modules. Alternatively, the data can be distributed using otheralgorithms, e.g., byte or block interleaving. In general, this increasesbandwidth, for instance, by allowing a volume in a SAN or a file innetwork attached storage to be read from or written to more than onegiven storage device 50 at a time. However, this technique requirescoordination among the various storage devices, and in practice mayrequire complex provisions for any failure of the storage devices, and astrategy for dealing with error checking information, e.g., a techniquefor storing parity information relating to distributed data. Indeed,when logical unit partitions are distributed in sufficiently smallgranularity, data associated with a single logical unit may span all ofthe storage devices 50.

While such hardware is not explicitly shown for purposes of illustrativesimplicity, clustered storage controller 34 may be adapted forimplementation in conjunction with certain hardware, such as a rackmount system, a midplane, and/or a backplane. Indeed, private network 46in one embodiment may be implemented using a backplane. Additionalhardware such as the aforementioned switches, processors, controllers,memory devices, and the like may also be incorporated into clusteredstorage controller 34 and elsewhere within storage subsystem 20, againas the skilled artisan will appreciate. Further, a variety of softwarecomponents, operating systems, firmware, and the like may be integratedinto one storage subsystem 20.

Storage devices 50 may comprise a combination of high capacity hard diskdrives and solid state disk drives. In some embodiments each of storagedevices 50 may comprise a logical storage device. In storage systemsimplementing the Small Computer System Interface (SCSI) protocol, eachof the logical storage devices may be referred to as a logical unit, andwhen made accessible by a given host computer 22, a logical unit number(LUN). While each LUN can be addressed as a single logical unit, the LUNmay comprise a combination of high capacity hard disk drives and/orsolid state disk drives.

FIG. 2 is a block diagram of a given module 36, in accordance with afirst embodiment of the present invention. In embodiments describedherein, each storage device 50 is divided into multiple storage units 60(also referred to herein as blocks or data blocks), wherein each of thestorage units comprises a sequence of bytes having a fixed size. Whilethe example shown in FIG. 2 shows each storage unit 60 stored on asingle storage device, each of the storage unit may comprise multiple“slices” of storage space spread among multiple storage devices 50.

Module 36 comprises a module processor 62 and a memory 64 that isconfigured to store a storage pool definition table 66 having entries68, a grouped pool definition table 70 having entries 72, a volumedefinition table 74 having entries 76 and a storage mapping table 78having entries 80. In operation, a manager node (not shown) in storagecontroller 34 can be configured to manage one or more storage pools, andto manage one or more data volumes within each of the one or morestorage pools.

Each given storage pool on storage controller 34 has a correspondingentry 68 in storage pool definition table 66 that stores metadatadefining the given storage pool. Each entry 68 comprises a storage poolidentifier 82, a pool attribute 84, a pool logical size 86 and a poolphysical size 88. Pool logical size 86 comprises a number of logicalstorage units 60 that are available to the given storage pool, and poolphysical size 88 comprises a number of physical storage units 60 thatare available to the given storage pool.

Attributes 84 describe how data in the given pool is stored. Examples ofattributes 84 include, but are not limited to, a pool type indictor, anda storage class. The pool type indicator can indicate if the givenstorage pool is a thick pool or a thin pool. Typically, volumes createdin a given storage pool inherit attributes (e.g., the pool typeindicator) of the given storage pool. In other words, volumes created inthick pools are thick volumes and volumes created in thin pools are thinvolumes. In embodiments where storage devices 50 comprises a combinationof small capacity fast hard disks, large capacity slower hard disks andsolid state drives (SSDs), the storage class attribute can indicatewhich type of storage device(s) 50 to be used to provide storage units60 to the given pool. Additional examples of devices 50 include, but arenot limited to, serial advanced SCSI (SAS) drives and serial ATAadvanced technology attachment (SATA) drives.

In operation, a given host computer 22 may implement a virtualizedenvironment having virtualized storage by executing a hypervisor such asESX™ or ESXi™, which are produced by VMware Inc., Palo Alto Calif. Toimplement an application program virtualized environment, storagecontroller 34 may be coupled to a vStorage APIs for Storage Awareness(VASA™) provider module 107 comprising a VASA processor 108 and a VASAmemory 109. When executing a hypervisor, VASA provider module 107provides a given host computer 22 with a set of APIs that enable storagecontroller 34 to interact with the hypervisor for managementfunctionality.

As explained hereinbelow, processor 62 can combine multiple storagepools to create a grouped pool. In other words, the grouped pool hasmultiple “sub-pools”. Grouped pools can be configured to have acapability to move storage units 60 between their respective sub-pools.

Each given grouped pool on storage controller 34 has one or morecorresponding entries 72 in grouped pool definition table 70 that storeinformation on the storage pools that make up the given grouped pool.Each entry 72 comprises a grouped pool identifier 90 and a storage poolidentifier 92. For example, if a given grouped pool comprises threestorage pools, then grouped pool definition table can store threeentries 72 for the given storage pool, wherein each of the three entriesstore a storage pool identifier for the given grouped pool and adistinct storage pool identifier 92. In an alternative implementation, agiven pool identifier 90 can have one or more storage pool identifiers92.

Each given data volume on storage controller 34 has a correspondingentry 76 in volume definition table 74 that stores metadata defining thegiven volume. Each entry 76 comprises a volume identifier 94, a volumesize 96, a volume allocated size 98 and storage pool identifier 100.Storage pool identifier 100 identifies a given storage pool that canused when allocating physical and/or logical storage units 60 to thegiven volume. As described supra, the given storage pool indicates ifthe given volume is a thin volume or a thick volume.

Each given storage unit 60 storage devices 50 has a corresponding entry80 in storage mapping table 78 that indicates a status of the givenstorage unit. Each entry 80 comprises a storage unit identifier 102, avolume identifier 104 and storage pool identifier 106. If the givenstorage unit is not being used by storage controller 34, then volumeidentifier 104 and storage pool identifier 106 are both null. If thegiven storage unit is currently assigned to a given storage pool but isnot currently assigned to a given data volume, then volume identifier104 is null and storage pool identifier 106 indicates the given storagepool. If the given storage unit is currently assigned to a given datavolume, then volume identifier 104 indicates the given data volume andstorage pool identifier 106 indicates the given storage pool.

Processors 62 and 108 typically comprise a general-purpose computer,which are programmed in software to carry out the functions describedherein. The software may be downloaded to module 36 and VASA module 107in electronic form, over a network, for example, or it may be providedon non-transitory tangible media, such as optical, magnetic orelectronic memory media. Alternatively, some or all of the functions ofthe processors may be carried out by dedicated or programmable digitalhardware components, or using a combination of hardware and softwareelements.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system”.Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Python, Java, Smalltalk, C++ or the like and conventionalprocedural programming languages, such as the “C” programming languageor similar programming languages. The program code may execute entirelyon the user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks. These computerprogram instructions may also be stored in a computer readable mediumthat can direct a computer, other programmable data processingapparatus, or other devices to function in a particular manner, suchthat the instructions stored in the computer readable medium produce anarticle of manufacture including instructions which implement thefunction/act specified in the flowchart and/or block diagram block orblocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Creating a Thick Data Volume in a Thin Pool

FIG. 3 is a flow diagram that schematically illustrates a method ofcreating a thick data volume using storage units 60 from a thin pool, inaccordance with an embodiment of the present invention. In aninitialization step 110, processor 62 initializes storage device 50. Toinitialize storage device 50, processor 62 first configures storagedevice as multiple storage units 60 so that each of the storage unitshas a storage granularity (i.e., a fixed size).

In a configuration step 112, processor 62 configures a thin provisionedstorage pool (also referred to herein as a thin pool) by assigning alogical number of storage units 60 and a physical number of storageunits 60 to the thin pool. The assigned number logical number of storageunits 60 comprises the thin pool's logical size, and the assigned numberof physical storage units 60 comprises the thin pool's physical size. Inthe thin provisioned storage pool, the physical number is less than thelogical number (i.e., the thin pool's physical size is smaller than thethin pool's logical size).

While configuring the thin pool, processor 62 can add a given entry 68to table 66, populate the given entry 69 with the thin pool's metadata,identify one or more entries 80 in storage mapping table 78 that areassociated with the storage units assigned to the thin pool, and updatethe storage pool identifier in the identified one or more entries 80 toindicate that the one or more storage units 60 are assigned to the thinpool.

In a receive step 114, processor 62 receives a request to create a thickdata volume comprising a requested number of storage units 60 from thethin pool, and upon receiving the request, in an identification step116, the processor identifies available number of storage units 60 thatare available in the thin pool. In the configuration shown in FIG. 2,the available number of storage units 60 comprises pool physical size 88in a given entry 68 in storage pool definition table 66 whose storagepool identifier 82 matches the thin pool.

In a comparison step 118, if the thin pool has a sufficient number ofstorage units 60 to create the requested thick volume, then in anallocation step 120, processor 62 allocates the requested number ofstorage units 60 to the volume and the method ends. Returning to step118, if the thin pool does not have a sufficient number of storage units60 to create the requested thick volume, then in a fail step 122,processor 62 fails the volume creation request, and the method ends.

In some embodiments, processor 62 can determine an available number ofphysical storage units based on a number of data volumes in the thinprovisioned storage pool and a respective amount of data stored in eachof the data volumes. To detect if the thin pool has a sufficient numberof storage units 60, processor 62 can check if the requested number isless than the available number, and the processor can allocate therequested number of storage units 60 by first adding an entry 76 tovolume definition table 74, and in the added entry, updating volumeidentifier 94 to indicate the requested thick volume, storing therequested number of storage units 60 to volume logical size 96 andvolume allocated size 98, and updating storage pool identifier 100 toindicate the thick pool.

Processor 62 can then identify the requested number of entries 80 instorage mapping table 78 where volume identifier 104 indicates the thinpool and volume identifier 104 is null (i.e., the storage units with theidentified entries are allocated to the thin pool but are not allocatedto any data volume) and update volume identifier 104 in the identifiedentry/entries (80) to indicate the requested thick volume. Finally,processor 62 can locate the entry 68 in storage pool definition table 66for the thick pool, and in the located entry 68, and reduce pool logicalsize 86 and pool physical size 88 by the requested number of storageunits 60.

In some embodiments, processor 62 can determine a number of logicalstorage units that are available in the thin pool, and allocate therequested number of storage units 60 from the thin pool upon determiningthat the requested number of storage units is less than the number ofthe logical storage units that are available in the thin pool. Inoperation, processor 62 can determine the number of logical storageunits that are available in the thin provisioned storage pool based anumber of data volumes in the thin provisioned storage pool and thestorage granularity. In further embodiments, upon checking the availablenumber of logical storage units, processor 62 can fail the request(similar to step 122) upon determining that the requested number isgreater than or equal to the available number of logical storage units.

Storing Volumes End-to-End

Storage systems that store data to fixed sized blocks such as storageunits 60 may waste storage resources if data volumes use less space thanthe size (also referred to herein as a granularity) of the fixed sizedblocks. For example, if the granularity is 16 GB and the storage systemstores ten 4 GB volumes, then the storage system typically allocates a16 GB storage unit 60 to each volume, thereby allocating 160 GB ofstorage space to store 40 GB of data. Similarly, if the storage systemallocates two 16 GB storage units 60 to store an 18 GB volume, then thestorage system allocated 14 GB of extra storage space to the volume.

FIGS. 4A and 4B are block diagrams of storage units 60 storing multipledata volumes 130 in an end-to-end configuration, and FIG. 5 is a flowdiagram that schematically illustrates a method of storing the datavolumes in the end-to-end configuration, in accordance with anembodiment of the present invention. The example shown in FIGS. 4A and4B shows three storage units 60, each having a granularity of 12 GB,that can be differentiated by appending a letter to the identifyingnumeral, so that the storage units comprise storage units 60A-60C.Likewise, the seven data volumes 130 shown in the figure can bedifferentiated by appending a letter to the identifying numeral, so thatthe data volumes comprise data volumes 130A-130G.

In an initialization step 140, processor 62 initializes storage device50. To initialize storage device 50, processor 62 first configuresstorage devices 50 as multiple storage units 60 so that each of thestorage units has a storage granularity (i.e., a fixed size).

In a receive step 142, processor 62 receives a request to createmultiple volumes 130, each the requested multiple of the data volumeshaving a requested maximum physical size. In a determination step 144,processor 62 determines, in response to the storage granularity, aminimum number of storage units 60 that are needed to store the multiplevolumes in an end-to-end configuration, wherein the number comprises aminimum multiple of the storage granularity number of storage units 60whose total storage size is greater than or equal to a total of therequested physical sizes.

To determine the minimum number of storage units 60, processor 62 canround up the total of the requested physical sizes to the next multipleof the storage granularity. For example, if the storage granularity is12 GB and the total of the requested physical sizes is 6 GB, then theminimum number of storage units 60 is one (i.e., one 12 GB granularity).Similarly, if the total of the requested physical sizes is 16 GB, thenthe minimum number of storage units 60 is two (i.e., two 12 GBgranularities comprising 24 GB of storage space).

In an allocation step 146, processor 62 allocates the determined numberof storage units 60 from a given storage pool to the multiple datavolumes. Finally, in a storing step 148, processor 62 stores themultiple volumes to the allocated storage unit(s) 60 in an end-to-endconfiguration, and the method ends. In other words, when storing themultiple volume in the end-to-end configuration, processor 62 stores themultiple volumes contiguously to the allocated storage unit(s) 60 as ifthe multiple volumes were a single volume.

In the example shown in FIG. 4A, the multiple volumes comprise volumes130A, 130B and 130C having a total requested physical size of 12 GB,where volume 130A has a physical size of 5 GB, volume 130B has aphysical size of 2 GB and volume 130C has a physical size of 6 GB. Since12 GB is also the storage granularity of storage units 60, processor 62can allocate a single storage unit 60A to store volumes 130A-130C in anend-to-end configuration (and with no wasted storage space) as shown inFIG. 4A.

In embodiments where a single given storage unit 60 is allocated to asingle given volume 130, storage mapping table has a single given entry80 for the given storage unit, and the volume identifier in the givenentry indicates the given volume. However, in embodiments whereprocessor 62 allocates the given storage unit 60 to multiple volumes130, storage mapping table 78 can have a distinct entry for each of themultiple volumes, and an offset (not shown) can be included in thedistinct entries.

In the example shown in FIG. 4A, processor 62 can add three entries 80to storage mapping table 78. In a first added entry, volume identifier104 can reference volume 130A, storage unit identifier 102 can referencethe given storage unit having a respective offset of “0” (i.e., data forvolume 130A is stored at the beginning of the given storage unit). In asecond added entry, volume identifier 104 can reference volume 130B,storage unit identifier 102 can reference the given storage unit havinga respective offset of “5” (i.e., data for volume 130A is storedstarting at the fifth gigabyte of the given storage unit). Finally, in athird added entry, volume identifier 104 can reference volume 130C,storage unit identifier 102 can reference the given storage unit havinga respective offset of “7” (i.e., data for volume 130C is storedstarting at the fifth gigabyte of the given storage unit).

In the example shown in FIG. 4B, the multiple volumes comprise volumes130D, 130E, 130F and 130G, wherein each of the volumes has a physicalsize of 5 GB, and the total or the requested physical sizes is 20 GB.Since storage units 60 have a storage granularity of 12 GB, processor 62can allocate two storage units 60B and 60C to store volumes 130D-130G inan end-to-end configuration as shown in FIG. 4B. Since the totalrequested physical size of 20 GB is less than two storage granularities(24 GB), example shown in FIG. 4B has 4 GB of unused space 132.Additionally, as shown in the figure, processor 62 can configure volume13F to span storage units 60A and 60B.

While the method presented in the flow diagram of FIG. 5 shows processor62 allocating multiple volumes 130 at a single time, subsequentlystoring an additional volume 130 to a given storage unit 60 in anend-to-end configuration is considered to be within the spirit and scopeof the present invention using the following logic:

BEGIN Receive a request to store an additional volume having a requestedsize; IF requested size >= the granularity Allocate a minimum number ofstorage units needed to store the additional volume; Store theadditional volume to the allocated storage unit(s); ELSEIF a previouslyallocated storage unit having unused storage space is located IF theunused space >= requested size Store the additional volume to theidentified storage unit in an end-to-end configuration; ELSE Allocate astorage unit to the additional volume; Store the additional volume tothe storage unit; ENDIF ENDIF END

Defining and Managing Grouped Pools

As described supra, a given storage pool can be either a thick pool or athin pool. Embodiments of the present invention provide methods andsystems for defining a third type of pool called a grouped pool. A givengrouped pool comprises at least two sub-pools comprising any combinationof thin pools and/or thick pools.

FIG. 6 is a flow diagram that schematically illustrates a method ofmanaging storage units 60 in a grouped pool, in accordance with anembodiment of the present invention. In an initialization step 150,processor 62 initializes storage devices 50. To initialize storagedevice 50, processor 62 first configures storage device as multiplestorage units 60 so that each of the storage units has a storagegranularity (i.e., a fixed size).

In a configuration step 152, processor 62 configures zero or more thinprovisioned storage pools (also referred to herein as thin pools) andzero or more thick provisioned storage pools (also referred to herein asthick pools) in order to configure multiple storage pools. Inembodiments of the present invention, processor 62 can configure anycombination of thin and/or thick pools as long as at least two storagepools are configured.

To configure a given storage pool, processor 62 can assign an initiallogical number of storage units 60 and an initial physical number ofstorage units 60 to the given storage pool. The assigned number logicalnumber of storage units 60 comprises the given storage pool's logicalsize, and the assigned number of physical storage units 60 comprises thegiven storage pool's physical size.

While configuring the given storage pool, processor 62 can add a givenentry 68 to table 66, populate the given entry 69 with the given pool'smetadata, identify one or more entries 80 in storage mapping table 78that are associated with the storage units assigned to the thin pool,and update the storage pool identifier in the identified one or moreentries 80 to indicate that the one or more storage units 60 areassigned to the given pool.

Upon configuring the storage pools in step 152, processor 62 canallocate a respective number of storage units 60 to each of the storagepools. In some embodiments, as explained hereinbelow, the respectivenumber of storage units 60 for a given storage pool configured as athick pool may be zero.

In a definition step 154, processor 62 defines a grouped pool comprisingone or more of the storage pools configured in step 152. For example,processor 62 can define a grouped storage pool comprising one thin pooland two thick pools. To define a grouped storage pool comprising onethin pool and two thick pools, processor 62 can first add three entries72 to grouped pool definition 70. Processor 62 can then update the firstadded entry 72 so that grouped pool identifier 90 indicates the definedgrouped pool and storage pool identifier 92 indicates the thick poolthat is to be included in the grouped pool, update the second addedentry 72 so that grouped pool identifier 90 indicates the definedgrouped pool and storage pool identifier 92 indicates the first of thethin pools that is to be included in the grouped pool, and update thethird added entry 72 so that grouped pool identifier 90 indicates thedefined grouped pool and storage pool identifier 92 indicates the secondof the thin pools that is to be included in the grouped pool.

In a first comparison step 156, if processor 62 receives a request toadd a data volume to the grouped pool, the request including one or morevolume attributes, then in an identification step 158, the processorcompares the one or more volume attributes to each of the one or morepool attributes of each storage pool in the grouped pool, and identifiesa given storage pool in response to the comparison. In other words,processor 62 identifies a given storage pool whose respective poolattribute(s) are most similar to the requested volume attributes inorder to identify a best matching storage pool in the grouped pool.

To identify the best matching storage pool, the request may include oneor more attributes for the requested volume, and processor 62 cancalculate a volume score using the received one or more volumeattributes, calculate, for each respective storage pool in the groupedpool, a respective pool score using the respective storage pool's one ormore pool attributes, and identify the given pool whose respective poolscore is closest to the volume score.

Examples of volume attributes include, but are not limited to:

A volume type indicating if the requested volume comprises (a) a thinvolume having a first physical size (i.e., a number of physical storageunits 60) and a second logical size (i.e., a number of logical storageunits 60), the first number less than the second number, (b) a thinvolume having a third physical size and a fourth logical size, the thirdnumber equal to the fourth number, and (c) a thin volume having a fifthphysical size and a fifth logical size, the fifth number equal to thesixth number.

A storage class for the volume that indicates a preferred storage devicetype for the volume. Examples of storage classes include, but are notlimited to disk drives, solid state drives (SSDs), serial advanced SCSI(SAS) drives and serial ATA advanced technology attachment (SATA)drives. For example, when defining a given data volume a systemadministrator can indicate, in the request, a preferred storage class.

An identity of a virtual machine that stores the volume. As describedsupra, if processor 62 executes a hypervisor to implement virtualizedstorage, a given pool attribute 84 can indicate an identity of a givenvirtual machine associated with a given data volume (i.e., a given SLU),and in instances where the processor receives the request from a givenvirtual machine, then the processor may assign a higher score to a firststorage pool storing an existing volume for the virtual machine and alower score to a second storage pool not storing any volumes for thevirtual machine.

A volume size. The requested volume's size can indicate the requestednumber of number of storage units 60 for the requested volume. Inoperation processor 62 can assign a higher score as a function of howthe requested number of storage units 60 “fits” into each of the storagepools. By scoring the entity sizes, processor 62 can locate a “best fit”for the requested data volume.

Examples of pool types include, but are not limited to:

A pool type indicating if a given storage pool is a thick pool or a thinpool.

A pool storage class indicating a type of storage devices used to storethe storage units in a given pool. Examples of pool storage classesinclude disk drives, SSDs, SAS drives and SATA drives.

An identity of a virtual machine. As described supra, if processor 62executes a hypervisor to implement virtualized storage, a given poolattribute 84 can indicate an identity of a given virtual machineassociated with a given storage pool. As described supra, upon processorreceive a volume creation request from a given virtual machine,processor 62 may assign a higher score to a first storage pool storingan existing volume for the virtual machine and a lower score to a secondstorage pool not storing any volumes for the given virtual machine.

Available space. A given pool's available space can indicate a number ofavailable (i.e., not allocated to any data volume) storage units 60. Asdescribed supra, upon receiving a request to create a data volume havinga requested size, processor 62 can assign a higher score as a functionof how the requested number of storage units 60 “fits” into each of thestorage pools.

In a second comparison step 160, if processor 62 detects that theidentified “best matching” storage pool has the requested number ofstorage units 60 available, then in a first allocation step 162 theprocessor allocates the requested number of storage units 60 in theidentified storage pool to the requested volume. However, if therequested number of storage units 60 is greater than the number ofstorage units available in the identified pool, then in a secondallocation step 164, processor 62 computes a number comprising theavailable amount of storage units subtracted from the requested numberof storage units, transfers the computed number of storage units 60 fromanother storage pool in the grouped pool, and upon performing thetransfer, allocates the requested number of the storage units to therequested volume.

To determine how many storage units 60 need to be transferred, processor62 can compute a number comprising the available amount of storage unitsin the identified pool subtracted from the requested number of storageunits. Upon computing the number, processor 62 can then transfer, withinthe grouped pool (i.e., from another storage pool in the grouped pool)the computed number of storage units 60 to the identified storage pool.

In some embodiments, the identified pool comprises a first given pool,and processor 62 can transfer the computed number of the storage unitsby identifying a second given storage pool in the grouped pool havingthe computed number of storage units available, and transferring thecomputed number of storage units from the second given storage pool tothe first given storage pool. For example, in step 154 processor 62 candefine a grouped pool having a first given storage pool comprising athick pool and a second given storage pool comprising a thin pool, andallocate all the logical and physical storage units 60 to the thin pool.In other words, no logical and/or physical regions are initiallyassigned to the thick pool.

In this example, upon receiving a request to create, in the groupedpool, a thick volume having a requested number of storage units 60,processor 62 can transfer the requested number of storage units (i.e.,both physical and logical) from the thin pool to the thin pool andallocate the transferred storage units 60 to the requested volume. Upontransferring the requested number of storage units 60 from the thin poolto the thick pool, processor 62 can reduce the thin pool's logicalnumber of storage units (i.e., logical size) and physical number ofstorage units (i.e., physical size) by the requested number.

Therefore, in this example, the thick pool is always 100% utilized,since all logical and physical storage units in the thick pool areassigned to one or more volumes.

In a third comparison step 166, if, in configurations implementing thisexample, processor 62 receives a request to delete the thick volume fromthe grouped pool's thick pool, then upon deleting the thick volume, theprocessor transfers the thick volumes storage unit(s) 60 back to thegrouped pool's thin pool in a transfer step 168, increments thin pool'slogical number of storage units and physical number of storage units bythe requested number, and the method continues with step 156.

Returning to step 166, if processor 62 does not receive a request todelete a thick volume from the grouped pool's thick pool, then themethod continues with step 156. Returning to step 156, if processor 62does not receive a request to add a data volume to the grouped pool,then the method continues with step 166.

In some embodiments, some or all the steps in the flow diagram shown inFIG. 6 may be performed by VASA processor 107 (i.e., instead of moduleprocessor 62 as described supra).

As described supra, when implementing storage virtualization, processor62 can create a “meta” volume for each virtual machine instanceexecuting on the processor. In embodiments of the present invention,processor 62 can create a grouped pool comprising a single thick pooland two thin pools for each virtual machine instance. In operation, thegrouped can allow free (physical) storage units 60 to be moved betweenany two pools in the grouped pool in a single atomic operation thatenables storage automation to move resources in real time thus easilyenabling a given set of storage units 60 to be used for thin or thickvolumes.

Storage automation enables a storage system to encapsulate timeconsuming or repetitive tasks into a best practices policy that can beinitiated on command or triggered via an event, with little or no humanintervention. Storage automation can include (a) automated provisioning,(b) capacity on demand, (c) host transparent data movement, (d) hot spotelimination, (e) transparent data migration, (f) information life cyclemanagement, and (g) utility storage. Among the issues confrontingstorage arrays implementing storage automation are concurrent mappingrequests and maintaining consistent mapping.

In operation, the thick pool and a first of the thin pools can be usedto store data volumes. The logical size of thin volumes in the firstthin pool can be calculated using standard business and best practices.The second thin pool can used as a meta pool to store all the metavolumes (i.e. any volume that does not represent a guest operatingsystem disk image or a snapshot). Given a specific hypervisortechnology, one or more standard size of the meta volumes can bedetermined (e.g. a size of the meta volumes holding configurationinformation, average memory size etc.). Using these standard sizes, analgorithm can be defined that not only determines the correct size ofthe meta pool based on the number of virtual machines to be supportedper container, but more importantly a correct logical size of the volumecan be determined to properly plan the correct physical and logicalsize. This is extremely important where storage arrays have large volumegranularity (e.g., greater than 10 GB) and the hypervisor has many metavolumes whose size is at least 50% smaller than the granularity. Withoutan ability to properly plan space allocation for the meta-volumes thepools may appear to quickly run out of logical resources well beforephysical resources are exhausted.

In some embodiments, an algorithm can used to determine a correct sizeof the meta pool based upon number of virtual machines and their averagememory sizes, thereby enabling storage systems to pre-create multiplemeta-volumes. When creating multiple small volumes at once, embodimentsof the present invention can enable to storage system to be more spaceefficient and pack multiple meta-volumes together into a single storagegranularity that would have previously been used by a single volume ifthe single volume was created alone.

Additionally, processor 62 can report space usage as a number of storageunits 60 that are allocated to DATA volumes, and in terms ofallocated/supported VMs, for example:

-   -   207/800 VMs allocate        thereby enabling the storage administrator to perform capacity        planning more effectively.

In operation, processor 62 can execute a software application that asksa system administrator to enter, via a system console (not shown), adesired number of virtual machine (VM) instances to execute via ahypervisor, and an average memory and disk size for the instances.Additionally, when implementing thin provisioned storage, theadministrator's input can indicate a percentage it should be physicallyallocating and a target amount of over provisioning.

Upon receiving the input from the system administrator, processor 62 cancreate a thick pool M whose size can be determined using the formula:

(NumVMs)*(TotalStorageSize)*(100−ThinStorage/100)  (1)

where NumVMs comprises a requested number of VMs, TotalStorageSizecomprises an amount of available storage, and ThinStorage comprises apercentage of TotalStorageSize. Processor 62 can then to create a thinpool N whose physical size is calculated using the formula:

PhysicalSize=(NumVMs)*(TotalStorageSize)*(100−ThinStorage/100)  (2)

and whose logical size is calculated using the formula:

(ThickSize)*(Overprovision)  (3)

where ThickSize comprises a size of thick volumes in the thin pool andOverprovision comprises a percentage (i.e., >100%) indicating an amountof overprovisioning.

Processor 62 can then create a thin meta pool O whose size that can bedetermined by the hypervisor's meta volume set. Given that each VM has avolume A of size X and a volume B of size Y, the following formulas canbe used to calculate an the physical and the logical sizes:

PhysicalSize=(NumVols)*(X+Y+ . . . )  (4)

LogicalSize=(NumVols)*(granularity/Y+granularity/Y+ . . . )  (5)

where NumVols comprises a number of requested data volumes in the thinpool and granularity comprises the storage array's storage granularity.

Processor 62 can then create a grouped pool pool_name using thefollowing function call:

grouped_pool_create gp=pool_name thick=M thin=N meta=0  (6)

The final step is for processor 62 to pre-create the meta volumes. Thenumber of meta volumes to be created can be determined as a percentageof total VMs, or a fixed number (e.g. 10) or can be determined by usinga multiple of the storage granularity to calculate a number that wouldminimize any remaining storage space in the system. This calculatednumber n may be different for each meta volume. Given n and size Xprocessor 62 can execute the following function:

create_multiple_volume size=X vol1=A1, A2, A3, A4, . . . , An−1, An  (7)

The final step is for processor 62 to pre-create the meta volumes. Thenumber of meta volumes to be created can be determined as a percentageof total VMs, or a fixed number (e.g. 10) or can be determined by usinga multiple of the storage granularity to calculate a number that wouldminimize any remaining storage space in the system. This calculatednumber n may be different for each meta volume. Given n and size Xprocessor 62 can execute the following function:

create_multiple_volume size=X, Y, X, Y, X, Y, X, Y, X, Y, X, Y, . . .vol1=A1, B1, A2, B2, A3, B3, A4, B4, . . . , An−1, Bn−1, An, Bn

In embodiments implementing storage automation, a storage automationentity can perform the following operations:

Maintain a pool of free meta-volumes and assign then to VMs uponreceiving requests to create each meta volume. When the pool is almostexhausted the storage automation entity can create a new set of metavolumes as described hereinabove.

Upon receiving requests to create a thin or thick volume the storageautomation entity create the requested volumes in either the thin or thethick pool determined by the type of volume(s) requested.

In embodiments where the storage system is configured to enable sharingphysical storage between thin and thick volumes, the storage automationentity can initially assign all physical storage to the thin pool. Aseach command is received to create a thick volumes, the storageautomation entity can first execute a command such as

grouped_pool_move_capacity gp=pool_name source=N target=M size=X  (8)

to move storage units 60 from the thin pool to the thick pool, and thencreate a thick volume in the thick pool using the moved storage units.Upon allocating the actual space that is needed to ensure that a thickvolume can be successfully created, the space can then be moved to thethick pool.

In order to simplify space reporting, when the hypervisor queries spacethe storage automation entity may report only on the combined status ofthe thin and thick pools. Additional the storage automation entity mayreport on the meta pools, however the entity may never report on themassive over provisioning of the meta pool but rather report thephysical size of the meta pool as being the meta pool physical andlogical size.

Upon receiving commands to create a volume that the storage automationentity identifies as a meta volume, the entity can ignore the requestedpool and always place the volumes in the meta volume. The response canindicate that the volume was created in the requested storage type, andif queried the storage automation entity can continue to report that thevolume was created when it was requested rather than when the volume wasactually created.

The flowchart(s) and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

It will be appreciated that the embodiments described above are cited byway of example, and that the present invention is not limited to whathas been particularly shown and described hereinabove. Rather, the scopeof the present invention includes both combinations and subcombinationsof the various features described hereinabove, as well as variations andmodifications thereof which would occur to persons skilled in the artupon reading the foregoing description and which are not disclosed inthe prior art.

What is claimed is:
 1. A storage system, comprising: one or more storagedevices; and a processor arranged: to configure the one or more storagedevices as a plurality of physical storage units, each of the physicalstorage units having a storage granularity, to configure, on the one ormore storage devices, a thin provisioned storage pool having a physicalnumber of the physical storage units and a logical number of logicalstorage units, the physical number being less than the logical number,and upon receiving a request to create a thick data volume having arequested number of the physical storage units: to identify an availablenumber of the physical storage units that are available in the thinprovisioned pool, and upon determining that the requested number is lessthan the available number, to allocate, from the thin provisionedstorage pool, the requested number of the physical storage units to thethick data volume.
 2. The storage system according to claim 1, whereinthe processor is configured to identify the available number of thephysical storage units based on a number of data volumes in the thinprovisioned storage pool and a respective amount of data stored in eachof the data volumes.
 3. The storage system according to claim 1, whereinthe processor is configured to determine the logical number of thelogical storage units that are available in the thin pool, and toallocate the requested number of the physical storage units from thethin pool upon determining that the requested number of the physicalstorage units is less than the logical number of the logical storageunits that are available in the thin pool.
 4. The storage systemaccording to claim 3, wherein the processor is configured to fail therequest upon determining that the requested number is greater than orequal to the number of the logical storage units that are available. 5.The storage system according to claim 3, wherein the processor isconfigured to determine the number of the logical storage units that areavailable in the thin provisioned storage pool based a number of datavolumes in the thin provisioned storage pool and the storagegranularity.
 6. The storage system according to claim 3, wherein uponallocating the requested number of the physical storage units, theprocessor is configured to subtract the requested number from theavailable physical number and to subtract the requested number from thenumber of the logical storage units that are available.
 7. The storagesystem according to claim 1, wherein the processor is configured to failthe request upon determining that the requested number is greater thanor equal to the available number of the physical storage units. 8-20.(canceled)
 21. A method, comprising: configuring one or more storagedevices as a plurality of physical storage units, each of the physicalstorage units having a storage granularity; configuring, on the one ormore storage devices, a thin provisioned storage pool having a physicalnumber of the physical storage units and a logical number of logicalstorage units, the physical number being less than the logical number;and upon receiving a request to create a thick data volume having arequested number of the physical storage units: identifying an availablenumber of the physical storage units that are available in the thinprovisioned pool; and upon determining that the requested number is lessthan the available number, allocating, from the thin provisioned storagepool, the requested number of the physical storage units to the thickdata volume.
 22. The method according to claim 21, wherein identifyingthe available number of the physical storage units comprises identifyingon a number of data volumes in the thin provisioned storage pool, andidentifying a respective amount of data stored in each of the datavolumes.
 23. The method according to claim 21, and comprisingdetermining the logical number of the logical storage units that areavailable in the thin pool, and allocating the requested number of thephysical storage units from the thin pool upon determining that therequested number of the physical storage units is less than the logicalnumber of the logical storage units that are available in the thin pool.24. The method according to claim 23, and comprising failing the requestupon determining that the requested number is greater than or equal tothe number of the logical storage units that are available.
 25. Themethod according to claim 23, wherein determining the number of thelogical storage units that are available in the thin provisioned storagepool comprises identifying a number of data volumes in the thinprovisioned storage pool, and identifying the storage granularity. 26.The method according to claim 23, and comprising upon allocating therequested number of the physical storage units, subtracting therequested number from the available physical number and to subtract therequested number from the number of the logical storage units that areavailable.
 27. The method according to claim 21, and comprising failingthe request upon determining that the requested number is greater thanor equal to the available number of the physical storage units.
 28. Acomputer program product, the computer program product comprising: anon-transitory computer readable storage medium having computer readableprogram code embodied therewith, the computer readable program codecomprising: computer readable program code arranged to configure one ormore storage devices as a plurality of physical storage units, each ofthe physical storage units having a storage granularity; computerreadable program code arranged to configure, on the one or more storagedevices, a thin provisioned storage pool having a physical number of thephysical storage units and a logical number of logical storage units,the physical number being less than the logical number; and uponreceiving a request to create a thick data volume having a requestednumber of the physical storage units: computer readable program codeconfigured to identify an available number of the physical storage unitsthat are available in the thin provisioned pool; and computer readableprogram code configured upon determining that the requested number isless than the available number, to allocate, from the thin provisionedstorage pool, the requested number of the physical storage units to thethick data volume.
 29. The computer program product according to claim28, wherein the computer readable program code is configured to identifythe available number of the physical storage units by identifying on anumber of data volumes in the thin provisioned storage pool, andidentifying a respective amount of data stored in each of the datavolumes.
 30. The computer program product according to claim 28, andcomprising computer readable program code configured to determine thelogical number of the logical storage units that are available in thethin pool, and to allocate the requested number of the physical storageunits from the thin pool upon determining that the requested number ofthe physical storage units is less than the logical number of thelogical storage units that are available in the thin pool.
 31. Thecomputer program product according to claim 30, and comprising computerreadable program code configured to fail the request upon determiningthat the requested number is greater than or equal to the number of thelogical storage units that are available.
 32. The computer programproduct according to claim 30, and comprising computer readable programcode configured upon allocating the requested number of the physicalstorage units, to subtract the requested number from the availablephysical number and to subtract the requested number from the number ofthe logical storage units that are available.
 33. The computer programproduct according to claim 28, and comprising computer readable programcode configured to fail the request upon determining that the requestednumber is greater than or equal to the available number of the physicalstorage units.